-
Notifications
You must be signed in to change notification settings - Fork 21
Introduce generic XY endpoint #132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce generic XY endpoint #132
Conversation
f7735fd to
b6a1fbf
Compare
bhufmann
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution. I reviewed and found a couples things to change.
API-proposed.yaml
Outdated
| format: int32 | ||
| filter_query_parameters: | ||
| $ref: "#/components/schemas/RequestedFilterQueryParameters" | ||
| RequestedFilterQueryParameters: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RequestedFilterQueryParameters already exists in this file (line 3423) and doesn't need to be added again.
API.yaml
Outdated
| format: int32 | ||
| filter_query_parameters: | ||
| $ref: "#/components/schemas/RequestedFilterQueryParameters" | ||
| RequestedFilterQueryParameters: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RequestedFilterQueryParameters already exists in this file (line 2902) and doesn't need to be added again.
API-proposed.yaml
Outdated
| $ref: "#/components/schemas/OutputElementStyle" | ||
| xValues: | ||
| xValuesDescription: | ||
| type: array |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is not correct, I think. It's not an array. The swagger documentation needs to be updated for that and the API regenerated.
API-proposed.yaml
Outdated
| axisDomain: | ||
| $ref: "#/components/schemas/AxisDomain" | ||
| yValuesDescription: | ||
| type: array |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is not correct, I think. It's not an array. The swagger documentation needs to be updated for that and the API regenerated.
API.yaml
Outdated
| xValuesDescription: | ||
| type: array | ||
| description: Series' X values | ||
| description: Series' X axis description |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same comment as for API_proposed.yaml
| description: Label for the axis | ||
| axisDomain: | ||
| $ref: "#/components/schemas/AxisDomain" | ||
| yValuesDescription: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same comment as for API_proposed.yaml
This endpoint is introduced to support xy chart that has a non-time x-axis proposed in eclipse-cdt-cloud#114 Signed-off-by: Siwei Zhang <[email protected]>
b6a1fbf to
8eab3f0
Compare
|
Fixed and created PR in incubator in: https://github.com/eclipse-tracecompass-incubator/org.eclipse.tracecompass.incubator/pull/215/files |
bhufmann
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Thanks for the update.
API-proposed.yaml
Outdated
| properties: | ||
| type: | ||
| type: string | ||
| description: "Type of axis domain (e.g., 'categorical' or 'timeRange')" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
timeRange -> range ?
API-proposed.yaml
Outdated
| type: | ||
| type: string | ||
| description: Type of axis domain | ||
| AxisDomainTimeRange: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AxisDomainRange ?
API.yaml
Outdated
| properties: | ||
| type: | ||
| type: string | ||
| description: "Type of axis domain (e.g., 'categorical' or 'timeRange')" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
timeRange -> range ?
API.yaml
Outdated
| type: | ||
| type: string | ||
| description: Type of axis domain | ||
| AxisDomainTimeRange: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AxisDomainRange
API-proposed.yaml
Outdated
| type: string | ||
| description: Label for the axis | ||
| axisDomain: | ||
| $ref: '#/components/schemas/AxisDomain' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be oneOf { AxisDomainCategorical, AxisDomainRange }, either here or directly in AxisDomain definition?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@siwei-zhang-work I think if you change the swagger annotation for AxisDomain to the following, then it will achieve what Patrick suggests:
@Schema(description = "Domain of values supported on a chart axis. Can be either categorical or numeric range.", oneOf = {
AxisDomainCategorical.class,
AxisDomainRange.class
})I uploaded the corresponding PR in the Trace Compass server code:
eclipse-tracecompass-incubator/org.eclipse.tracecompass.incubator#220
|
@siwei-zhang-work I pushed a commit on top of your branch used to generate this PR to include the incubator update and the fixes that Patrick pointed out. |
Signed-off-by: Bernd Hufmann <[email protected]>
bhufmann
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@siwei-zhang-work changes look good. Thanks!
This endpoint is introduced to support xy chart that has a non-time x-axis proposed in
#114
What it does
Introduce generic XY endpoint proposed in #114